Configuration and reconfiguration of aggregated backhaul bearers in a multi-hop integrated access backhaul network for 5G or other next generation network

ABSTRACT

In a 5G network, an integrated access and backhaul (IAB) deployment in a 5G network, can enable aggregation of multiple user equipment (UE) bearers into backhaul bearers based on factors such as route information of UE bearers and quality of service of UE bearers. Additionally, reconfiguration of backhaul bearers, based on triggers, such as route changes for UE bearers can increase network efficiency for a 5G or other next generation network.

RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/356,679 (now U.S. Pat. No.11,057,791), filed Mar. 18, 2019, and entitled “CONFIGURATION ANDRECONFIGURATION OF AGGREGATED BACKHAUL BEARERS IN A MULTI-HOP INTEGRATEDACCESS BACKHAUL NETWORK FOR 5G OR OTHER NEXT GENERATION NETWORK,” whichclaims the benefit of priority to U.S. Provisional Patent ApplicationNo. 62/752,555, filed Oct. 30, 2018 and titled “CONFIGURATION ANDRECONFIGURATION OF AGGREGATED BACKHAUL BEARERS IN A MULTI-HOP INTEGRATEDACCESS BACKHAUL NETWORK FOR 5G OR OTHER NEXT GENERATION NETWORK,” theentireties of which applications are incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates generally to facilitating configuration andreconfiguration of aggregated backhaul bearers for a 5G new radio (NR)networks. For example, this disclosure relates to configuration andreconfiguration of aggregated backhaul bearers in a multi-hop integratedaccess backhaul network for a 5G, or other next generation network, airinterface.

BACKGROUND

5th generation (5G) wireless systems represent a next major phase ofmobile telecommunications standards beyond the currenttelecommunications standards of 4^(th) generation (4G). Rather thanfaster peak Internet connection speeds, 5G planning aims at highercapacity than current 4G, allowing a higher number of mobile broadbandusers per area unit, and allowing consumption of higher or unlimiteddata quantities. This would enable a large portion of the population tostream high-definition media many hours per day with their mobiledevices, when out of reach of wireless fidelity hotspots. 5G researchand development also aims at improved support of machine-to-machinecommunication, also known as the Internet of things, aiming at lowercost, lower battery consumption, and lower latency than 4G equipment.

The above-described background relating to facilitating configurationand reconfiguration of aggregated backhaul bearers is merely intended toprovide a contextual overview of some current issues, and is notintended to be exhaustive. Other contextual information may becomefurther apparent upon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system in which anetwork node device (e.g., network node) and user equipment (UE) canimplement various aspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example schematic system block diagram of a newradio access architecture according to one or more embodiments.

FIG. 3 illustrates an example schematic system block diagram ofintegrated access and backhaul links according to one or moreembodiments.

FIG. 4 illustrates an example schematic system block diagram of a userplane protocol stack for a multi-hop integrated access backhaul relayscenario according to one or more embodiments.

FIG. 5 illustrates an example schematic system block diagram of anintegrated access backhaul architecture according to one or moreembodiments.

FIG. 6 illustrates an example schematic system block diagram of aquality of service bearer aggregation over backhaul links according toone or more embodiments.

FIG. 7 illustrates an example schematic system block diagram of a flowcontrol solution for an integrated access backhaul according to one ormore embodiments.

FIG. 8 illustrates an example schematic system block diagram of anintegrated access backhaul network according to one or more embodiments.

FIG. 9 illustrates an example flow diagram of a method that facilitatesconfiguration and reconfiguration of aggregated backhaul bearersaccording to one or more embodiments.

FIG. 10 illustrates an example flow diagram of a system that facilitatesconfiguration and reconfiguration of aggregated backhaul bearersaccording to one or more embodiments.

FIG. 11 illustrates an example flow diagram of a machine-readable mediumthat facilitates configuration and reconfiguration of aggregatedbackhaul bearers according to one or more embodiments.

FIG. 12 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitatessecure wireless communication according to one or more embodimentsdescribed herein.

FIG. 13 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of various embodiments. One skilled inthe relevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor, a process running on a processor, an object, anexecutable, a program, a storage device, and/or a computer. By way ofillustration, an application running on a server and the server can be acomponent. One or more components can reside within a process, and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Further, these components can execute from various machine-readablemedia having various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, a local areanetwork, a wide area network, etc. with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

The words “exemplary” and/or “demonstrative” are used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive—in a manner similar to the term “comprising” as an opentransition word—without precluding any additional or other elements.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, or machine-readable media. Forexample, computer-readable media can include, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media.

As an overview, various embodiments are described herein to facilitateconfiguration and reconfiguration of aggregated backhaul bearers for a5G or other next generation networks. For simplicity of explanation, themethods (or algorithms) are depicted and described as a series of acts.It is to be understood and appreciated that the various embodiments arenot limited by the acts illustrated and/or by the order of acts. Forexample, acts can occur in various orders and/or concurrently, and withother acts not presented or described herein. Furthermore, not allillustrated acts may be required to implement the methods. In addition,the methods could alternatively be represented as a series ofinterrelated states via a state diagram or events. Additionally, themethods described hereafter are capable of being stored on an article ofmanufacture (e.g., a machine-readable storage medium) to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media, including a non-transitory machine-readable storage medium.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G, Universal MobileTelecommunications System (UMTS), and/or Long Term Evolution (LTE), orother next generation networks, the disclosed aspects are not limited to5G, a UMTS implementation, and/or an LTE implementation as thetechniques can also be applied in 3G, 4G or LTE systems. For example,aspects or features of the disclosed embodiments can be exploited insubstantially any wireless communication technology. Such wirelesscommunication technologies can include UMTS, Code Division MultipleAccess (CDMA), Wi-Fi, Worldwide Interoperability for Microwave Access(WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS, ThirdGeneration Partnership Project (3GPP), LTE, Third Generation PartnershipProject 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access(HSPA), Evolved High Speed Packet Access (HSPA+), High-Speed DownlinkPacket Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Zigbee,or another IEEE 802.XX technology. Additionally, substantially allaspects disclosed herein can be exploited in legacy telecommunicationtechnologies.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate configurationand reconfiguration of aggregated backhaul bearers for a 5G network.Facilitating operation of integrated access backhaul under anon-standalone network architecture for a 5G network can be implementedin connection with any type of device with a connection to thecommunications network (e.g., a mobile handset, a computer, a handhelddevice, etc.) any Internet of things (IOT) device (e.g., toaster, coffeemaker, blinds, music players, speakers, etc.), and/or any connectedvehicles (cars, airplanes, space rockets, and/or other at leastpartially automated vehicles (e.g., drones)). In some embodiments thenon-limiting term user equipment (UE) is used. It can refer to any typeof wireless device that communicates with a radio network node in acellular or mobile communication system. Examples of UE are targetdevice, device to device (D2D) UE, machine type UE or UE capable ofmachine to machine (M2M) communication, PDA, Tablet, mobile terminals,smart phone, laptop embedded equipped (LEE), laptop mounted equipment(LME), USB dongles etc. Note that the terms element, elements andantenna ports can be interchangeably used but carry the same meaning inthis disclosure. The embodiments are applicable to single carrier aswell as to multicarrier (MC) or carrier aggregation (CA) operation ofthe UE. The term carrier aggregation (CA) is also called (e.g.interchangeably called) “multi-carrier system”, “multi-cell operation”,“multi-carrier operation”, “multi-carrier” transmission and/orreception.

In some embodiments the non-limiting term radio, network node, or simplynetwork node is used. It can refer to any type of network node thatserves UE is connected to other network nodes or network elements or anyradio node from where UE receives a signal. Examples of radio networknodes are Node B, base station (BS), multi-standard radio (MSR) nodesuch as MSR BS, eNode B, network controller, radio network controller(RNC), base station controller (BSC), relay, donor node controllingrelay, base transceiver station (BTS), access point (AP), transmissionpoints, transmission nodes, RRU, RRH, nodes in distributed antennasystem (DAS) etc.

Cloud radio access networks (RAN) can enable the implementation ofconcepts such as software-defined network (SDN) and network functionvirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openapplication programming interfaces (“APIs”) and move the network coretowards an all internet protocol (“IP”), cloud based, and softwaredriven telecommunications network. The SDN controller can work with, ortake the place of policy and charging rules function (“PCRF”) networkelements so that policies such as quality of service and trafficmanagement and routing can be synchronized and managed end to end.

To meet the huge demand for data centric applications, 4G standards canbe applied 5G, also called new radio (NR) access. 5G networks cancomprise the following: data rates of several tens of megabits persecond supported for tens of thousands of users; 1 gigabit per secondcan be offered simultaneously to tens of workers on the same officefloor; several hundreds of thousands of simultaneous connections can besupported for massive sensor deployments; spectral efficiency can beenhanced compared to 4G; improved coverage; enhanced signalingefficiency; and reduced latency compared to LTE. In multicarrier systemsuch as OFDM, each subcarrier can occupy bandwidth (e.g., subcarrierspacing). If the carriers use the same bandwidth spacing, then it can beconsidered a single numerology. However, if the carriers occupydifferent bandwidth and/or spacing, then it can be considered a multiplenumerology.

Topology management can comprise the following characteristics: 1)happens on long time scales; 2) manages static hop order; 3) handlesinitial access of relay nodes; and/or 4) changes every time a node isadded or removed. Alternatively, route management can happen at a muchfaster time scale (e.g., happens over 10 seconds, or 100s ofmilliseconds) and routes are updated for load variance and blocking.Depending on the network architecture, the scheduling of backhaul linkscan be performed by a central node (e.g., an aggregation point) or canbe distributed across multiple nodes, requiring coordination of resourceallocation and/or route selection information. For densely deployedmmWave NR systems, the area covered by an NR node can be small, so adense deployment of NR nodes in a given area can require a larger numberof deployment sites. When an integrated access backhaul (IAB) isdeployed in such an environment with sparse fiber deployment, the largenumber of deployment sites can create a deployment where multiple IABhops can be utilized to reach the IAB donor node (e.g., IAB donor hasaccess to fiber). This means that for each UE bearer, a particular routethrough the multi-hop network can be determined. Moreover, when channelor network conditions change dynamically, the route through themulti-hop IAB network can also change.

Furthermore, data from multiple UE bearers can be aggregated into commonbackhaul bearers that are established between two IAB nodes. Suchbackhaul bearers can be referred to as radio link control (RLC)channels. In this disclosure, three specific solutions are proposed. Thefirst solution comprises a configuration of many-to-one aggregatedbackhaul bearers between IAB nodes based on one or more factors,including routing information, quality of service (QoS), etc. of the UEbearers that are aggregated into the backhaul bearers. The secondsolution can comprise enforcement of aggregation policies, and the thirdsolution can comprise reconfiguration of already established aggregatedbackhaul bearers, based on mobility events and radio resource management(RRM) triggers such as route changes, link failures, etc. in the IABnetwork.

Donor units (DU) and relay DUs (IAB Node) can be connected by a relaylink between the two. UEs can send data from the relay link to the DU.Each UE can send this data, or the data can be aggregated. For example,if UE1 and UE2 have a similar type of service, then the packets of theUEs can be aggregated on the same relay bearer. UEs with similar typesof services can have their data aggregated. Alternatively, UE bearersthat will be sending data to the same set of access nodes can have theirdata aggregated as well. Thus, aggregation can be based on routingdecisions. Aggregation can also depend on reconfiguration and/or localcongestion conditions of the bearer or the IAB node. For example, ifsome things in the network change, then the bearer aggregation can bereconfigured.

Each of the IAB nodes can require routing information related to each ofthe UE bearers in order to decide which other UE bearer is suitable toaggregate with another UE bearer. If there is a centralized routingentity, the routing entity can enforce aggregation policies for IABnodes. Thus, it can provide guidance to the IAB nodes through anorchestration entity or a control plane interface. For example, thecentralized routing entity can ensure that certain aggregation policiesare enforced. Policies can also change, over time, based on network ortraffic conditions (e.g., more bearer aggregation, less beareraggregation, static bearer aggregation). The centralized routing entitycan also consider the total mix of different quality of class of bearersin the network. For example, if there are a lot of high quality classUEs, then the centralized routing entity may want the lower quality ofservice class bearers to be aggregated more so than the higher qualityclass bearers. Individual IAB nodes can also trigger topology changes tomaintain a certain performance. For example, if an IAB node realizesthat it cannot sustain a certain quality of service, then a topologychange can help alleviate the load of that IAB node, which can thentrigger the centralized routing entity to reevaluate the topology and/orenforce a change. In another embodiment, if one of the UEs performs ahandover, then the system can reconfigure how the UE bearers areaggregated into backhaul bearers because one of the UEs that wasaggregated into one backhaul bearer has now moved to a different nodethat can be better aggregated with another UE.

In one embodiment, described herein is a method comprising receiving, bya wireless network device comprising a processor, first data from afirst mobile device of a wireless network via a first mobile devicebearer channel. The method can also comprise receiving, by the wirelessnetwork device, second data from a second mobile device of the wirelessnetwork via a second mobile device bearer channel. Additionally, inresponse to the receiving the first data from the first mobile deviceand the receiving the second data from the second mobile device, themethod can comprise aggregating, by the wireless network device, thefirst data and the second data, resulting in aggregated data for abackhaul bearer of the wireless network, wherein the aggregating thefirst data and the second data is based on a first condition associatedwith a quality of service of the first mobile device bearer channelbeing determined to have been satisfied and a second conditionassociated with a data route of the first data being determined to havebeen satisfied.

According to another embodiment, a system can facilitate, receivingfirst data from a first mobile device via a first bearer channel of awireless network. The system can also comprise receiving second datafrom a second mobile device via a second bearer channel of the wirelessnetwork. Additionally, in response to the receiving the first data fromthe first mobile device and the receiving the second data from thesecond mobile device, and in response to an aggregation conditionassociated with a routing pattern and a quality of service beingdetermined to have been satisfied, the system can comprise aggregatingthe first data and the second data, resulting in aggregated data for usein connection with a backhaul bearer of the wireless network.

According to yet another embodiment, described herein is amachine-readable storage medium that can perform the operationscomprising receiving first data from a first mobile device via a firstbearer channel. The machine-readable storage medium can perform theoperations comprising receiving second data from a second mobile devicevia a second bearer channel. Furthermore, in response to the receivingthe first data from the first mobile device and the receiving the seconddata from the second mobile device and in response to a routingcondition and a quality of service of the second bearer channel beingdetermined to have been satisfied, the machine-readable storage mediumcan perform the operations comprising aggregating the first data and thesecond data, resulting in aggregated data to be utilized by a backhaulbearer.

These and other embodiments or implementations are described in moredetail below with reference to the drawings.

Referring now to FIG. 1 , illustrated is an example wirelesscommunication system 100 in accordance with various aspects andembodiments of the subject disclosure. In one or more embodiments,system 100 can comprise one or more UEs 102. The non-limiting term userequipment can refer to any type of device that can communicate with anetwork node in a cellular or mobile communication system. A UE can haveone or more antenna panels having vertical and horizontal elements.Examples of a UE comprise a target device, device to device (D2D) UE,machine type UE or UE capable of machine to machine (M2M)communications, personal digital assistant (PDA), tablet, mobileterminals, smart phone, laptop mounted equipment (LME), universal serialbus (USB) dongles enabled for mobile communications, a computer havingmobile capabilities, a mobile device such as cellular phone, a laptophaving laptop embedded equipment (LEE, such as a mobile broadbandadapter), a tablet computer having a mobile broadband adapter, awearable device, a virtual reality (VR) device, a heads-up display (HUD)device, a smart car, a machine-type communication (MTC) device, and thelike. User equipment UE 102 can also comprise IOT devices thatcommunicate wirelessly.

In various embodiments, system 100 is or comprises a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. In example embodiments, a UE 102 can becommunicatively coupled to the wireless communication network via anetwork node 104. The network node (e.g., network node device) cancommunicate with user equipment (UE), thus providing connectivitybetween the UE and the wider cellular network. The UE 102 can sendtransmission type recommendation data to the network node 104. Thetransmission type recommendation data can comprise a recommendation totransmit data via a closed loop MIMO mode and/or a rank-1 precoder mode.

A network node can have a cabinet and other protected enclosures, anantenna mast, and multiple antennas for performing various transmissionoperations (e.g., MIMO operations). Network nodes can serve severalcells, also called sectors, depending on the configuration and type ofantenna. In example embodiments, the UE 102 can send and/or receivecommunication data via a wireless link to the network node 104. Thedashed arrow lines from the network node 104 to the UE 102 representdownlink (DL) communications and the solid arrow lines from the UE 102to the network nodes 104 represents an uplink (UL) communication.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. The one or morecommunication service provider networks 106 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. For example, inat least one implementation, system 100 can be or include a large scalewireless communication network that spans various geographic areas.According to this implementation, the one or more communication serviceprovider networks 106 can be or include the wireless communicationnetwork and/or various additional devices and components of the wirelesscommunication network (e.g., additional network devices and cell,additional UEs, network server devices, etc.). The network node 104 canbe connected to the one or more communication service provider networks106 via one or more backhaul links 108. For example, the one or morebackhaul links 108 can comprise wired link components, such as a T1/E1phone line, a digital subscriber line (DSL) (e.g., either synchronous orasynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, acoaxial cable, and the like. The one or more backhaul links 108 can alsoinclude wireless link components, such as but not limited to,line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation).

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and the network node104). While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000 etc.

For example, system 100 can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system 100 are particularlydescribed wherein the devices (e.g., the UEs 102 and the network node104) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks are expected to fulfill the demand ofexponentially increasing data traffic and to allow people and machinesto enjoy gigabit data rates with virtually zero latency. Compared to 4G,5G supports more diverse traffic scenarios. For example, in addition tothe various types of data communication between conventional UEs (e.g.,phones, smartphones, tablets, PCs, televisions, Internet enabledtelevisions, etc.) supported by 4G networks, 5G networks can be employedto support data communication between smart cars in association withdriverless car environments, as well as machine type communications(MTCs). Considering the drastic different communication needs of thesedifferent traffic scenarios, the ability to dynamically configurewaveform parameters based on traffic scenarios while retaining thebenefits of multi carrier modulation schemes (e.g., OFDM and relatedschemes) can provide a significant contribution to the highspeed/capacity and low latency demands of 5G networks. With waveformsthat split the bandwidth into several sub-bands, different types ofservices can be accommodated in different sub-bands with the mostsuitable waveform and numerology, leading to an improved spectrumutilization for 5G networks.

To meet the demand for data centric applications, features of proposed5G networks may comprise: increased peak bit rate (e.g., 20 Gbps),larger data volume per unit area (e.g., high system spectralefficiency—for example about 3.5 times that of spectral efficiency oflong term evolution (LTE) systems), high capacity that allows moredevice connectivity both concurrently and instantaneously, lowerbattery/power consumption (which reduces energy and consumption costs),better connectivity regardless of the geographic region in which a useris located, a larger numbers of devices, lower infrastructuraldevelopment costs, and higher reliability of the communications. Thus,5G networks may allow for: data rates of several tens of megabits persecond should be supported for tens of thousands of users, 1 gigabit persecond to be offered simultaneously to tens of workers on the sameoffice floor, for example; several hundreds of thousands of simultaneousconnections to be supported for massive sensor deployments; improvedcoverage, enhanced signaling efficiency; reduced latency compared toLTE.

The upcoming 5G access network may utilize higher frequencies (e.g., >6GHz) to aid in increasing capacity. Currently, much of the millimeterwave (mmWave) spectrum, the band of spectrum between 30 gigahertz (GHz)and 300 GHz is underutilized. The millimeter waves have shorterwavelengths that range from 10 millimeters to 1 millimeter, and thesemmWave signals experience severe path loss, penetration loss, andfading. However, the shorter wavelength at mmWave frequencies alsoallows more antennas to be packed in the same physical dimension, whichallows for large-scale spatial multiplexing and highly directionalbeamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingcapacity of wireless systems. The use of multiple-input multiple-output(MIMO) techniques can improve mmWave communications, and has been widelyrecognized a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems, and are planned for use in 5G systems.

Referring now to FIG. 2 , illustrated is an example schematic systemblock diagram of a new radio access architecture according to one ormore embodiments. 3GPP NR-based 5G mobile networks can be deployed usinga split RAN protocol architecture such that on the user plane the packetdata convergence protocol (PDCP) sublayers can reside at a centralizedunit (CU), while the RLC, media access control (MAC), and physical layer(PHY) layers can reside at the distributed unit (DU). User plane datacan be carried on data radio bearers (DRBs) that traverse the abovedescribed user plane RAN protocol architecture. On the control plane,signaling radio bearers (SRBs) can be set up to carry control messagesfrom the RRC layer, also utilize the PDCP layer at the CU, and furthercarry the control messages down through the RLC, MAC, and PHY layers atthe DU to be delivered to the UE over the air interface. Each networkuser can be allocated multiple DRBs and SRBs by the network. The networkinterface between the CU and DU can be called the F1 interface per 3GPPspecifications.

Referring now to FIG. 3 , illustrated is an example schematic systemblock diagram of integrated access and backhaul links according to oneor more embodiments. An IAB feature can enable future cellular networkdeployment scenarios and applications to support wireless backhaul andrelay links enabling flexible and very dense deployment of NR cellswithout the need for densifying the transport network proportionately.

Due to the expected larger bandwidth available for NR compared to LTE(e.g. mmWave spectrum) along with the native deployment of massive MIMOor multi-beam systems in NR, IAB links can be developed and deployed.This can allow easier deployment of a dense network of self-backhauledNR cells in a more integrated manner by building upon many of thecontrol and data channels/procedures defined for providing access toUEs.

For example, the network 300, as represented in FIG. 3 with integratedaccess and backhaul links, can allow a relay node to multiplex accessand backhaul links in time, frequency, and/or space (e.g. beam-basedoperation). Thus, FIG. 3 illustrates a generic IAB setup comprising acore network 302, a centralized unit 304, donor distributed unit 306,relay distributed unit 308, and UEs 102 ₁, 102 ₂, 102 ₃. The donordistributed unit 306 (e.g., access point) can have a wired backhaul witha protocol stack and can relay the user traffic for the UEs 102 ₁, 102₂, 102 ₃ across the IAB and backhaul link. Then, the relay distributedunit 308 can take the backhaul link and convert it into differentstrains for the connected UEs 102 ₁, 102 ₂, 102 ₃. Although FIG. 3depicts a single hop (e.g., over the air), it should be noted thatmultiple backhaul hops can occur in other embodiments.

Referring now to FIG. 4 , illustrated is an example schematic systemblock diagram of a user plane protocol stack for a multi-hop integratedaccess backhaul relay scenario according to one or more embodiments. Inone embodiment, an adaptation layer can be placed above the RLC layer atthe IAB DUs. The adaptation layer can perform the tasks of routing of UEtraffic across the multi-hop network, and aggregation of bearers frommultiple UEs into common backhaul bearers. It should be noted that thedepicted protocol stack for the full RLC layer, including the automaticrepeat request (ARQ) functionality, resides at each IAB node. Thus, theRLC ARQ in this multi-hop relay network can be performed on a hop-by-hopbasis.

The protocol stack shown on the UE side comprises a physical (PHY)layer, medium access control (MAC) layer, radio link control (RLC)layer, packet data convergence protocol (PDCP) and session dataapplication protocol (SDAP) in the RAN protocol stack. The PDCP and SDAPare served from the UE to the IAB donor user plane central unit (CU-UP),where the PDCP and SDAP reside at the CU-UP on the network side. The IABserving node goes up to the RLC. The protocol stack from the mobiletermination (MT) of the serving IAB node to the DU of the IAB donor cancomprise an adaption (adapt) layer. The adapt layer can perform arouting function from one IAB node to another IAB node, and it canperform the function of bearer aggregation.

Referring now to FIG. 5 illustrated is an example schematic system blockdiagram of an integrated access backhaul architecture according to oneor more embodiments. Data from multiple UE bearers can be aggregatedinto common backhaul bearers that are established between two IAB nodes502 ₁, 502 ₂. Such backhaul bearers can be referred to as RLC channels.Within an IAB network, IAB nodes 502 ₁, 502 ₂ can comprise a DU that canconnect with the UEs 102 ₁, 102 ₂, 102 ₃. The IAB nodes 502 ₁, 502 ₂ canalso comprise an MT. Since the IAB node 502 ₁ is a relay, it can talk toanother IAB node 502 ₂. Thus, an RLC channel can be established betweenan MT of an IAB node 502 ₁ to a DU of another IAB node 502 ₂, whichforms the relay link for which the UE bearers and data can betransmitted. Thus, UEs 102 ₁, 102 ₂, 102 ₃ can be attached to the IABnodes 502 ₁, 502 ₂ to connect to a next generation core network (NGC)506, via an IAB donor node 504, which can be connected to the NCG 506through a wired interface. The IAB donor node 504 can comprise a centralunit (CU). The RLC, MAC, and PHY can be in the DU and the PDCP and theSDAP can be in the CU (as depicted by FIG. 4 ). Additionally, the DU andthe CU can be connected within the IAB Donor node 504 (e.g., basestation). As depicted in FIG. 5 , the CU can be connected to multipleDUs from various IAB nodes 502 ₁, 502 ₂, however, there can be only oneCU that connects the data back to the NGC 506.

Referring now to FIG. 6 , illustrated is an example schematic systemblock diagram of a quality of service bearer aggregation over backhaullinks according to one or more embodiments. FIG. 6 depicts the conceptof aggregating multiple UE bearers into a backhaul bearer based oncommon QoS profiles.

As depicted in FIG. 6 , the UE 102 ₁ can have two bearers (e.g., voiceover internet protocol (VOIP) and data streaming), the UE 102 ₂ can havetwo bearers (e.g., VOIP and web browsing), and the UE 102 ₃ can havethree bearers (e.g., VOIP, web browsing, and data streaming). When theUEs 102 ₁, 102 ₂, 102 ₃ connect to the first IAB node 502 ₁, and thefirst IAB node needs to relay all of the data from the UEs 102 ₁, 102 ₂,102 ₃ to the second IAB node 502 ₂, then the first IAB node 502 ₁ canaggregate the VOIP bearer for all three UEs 102 ₁, 102 ₂, 102 ₃ onto asingle RLC channel based on the type of bearer. For example, RLC channel1 can aggregate the VOIP data from all three UEs 102 ₁, 102 ₂, 102 ₃,RLC channel 2 can aggregate the web browsing data from UEs 102 ₂, 102 ₃,and RLC channel 3 can aggregate the streaming data from UEs 102 ₁, 102₃. Alternatively, the aggregation can be based on QoS and/or routes. Forexample, if UE 102 ₁, and UE 102 ₂ have a similar data route, then theirbearers (regardless of type of bearer) can be aggregated onto one RLCchannel, and the bearer for UE 102 ₃ can be placed a different RLCchannel.

Referring now to FIG. 7 , illustrated is an example schematic systemblock diagram of a flow control solution for an integrated accessbackhaul according to one or more embodiments. There can be various flowcontrol solutions specified to prevent congestion at IAB nodes. However,a couple of the main flow control candidates are depicted in FIG. 7 .There could be a hop-by-hop flow control mechanism between IAB nodes 502₁, 502 ₂, 502 ₃, or an end-to-end flow control mechanism between theaccess IAB node 502 ₁ and the donor IAB node 504. Thus, beareraggregation of UE 102 bearers can be performed based on routinginformation and flow control feedback, along with reconfiguration ofalready set up RLC channels or backhaul bearers based on mobility orradio resource management (RRM) events.

Referring now to FIG. 8 , illustrated is an example schematic systemblock diagram of an integrated access backhaul network according to oneor more embodiments. The IAB network configuration depicted in FIG. 8comprises four UEs (e.g., 102 ₁, 102 ₂, 102 ₃ 102 ₄) connected to an IABnetwork. The bearer for UE1 (e.g., 102 ₁) can traverse two IAB links viaIAB node 2 (e.g., 502 ₂) and IAB node 1 (e.g., 502 ₁) to reach the donorgNB-DU (e.g., 504). The bearers for UE2 (e.g., 102 ₂) and UE3 (e.g., 102₃) can traverse three IAB links via IAB node 3 (e.g., 502 ₃), IAB node 2(e.g., 502 ₂), and IAB node 1 (e.g., 502 ₁) to reach the donor gNB-DU(e.g., 504). Additionally, the UE bearer for UE4 (e.g., 102 ₄) cantraverse only two IAB links via IAB node 4 (e.g., 502 ₄) and IAB node 1(e.g., 502 ₁) to reach the gNB-DU (e.g., 504). It should be noted thatIAB node 3 (e.g., 502 ₃) can also connect to IAB node 4. In the event ofa link failure of link 3 between IAB node 3 (e.g., 502 ₃) and IAB node 2(e.g., 502 ₂), traffic for UE2 and UE3 can be routed via IAB node 4(e.g., 502 ₄). For simplicity of discussion, assume that all UEs areperforming services that require the same QoS class of bearers.

In the above described network example, under existing QoS-based beareraggregation over backhaul bearers, for IAB link 1, the bearers for allthree UEs (e.g., 102 ₁, 102 ₂, 102 ₃) can be aggregated into the samebackhaul bearer between IAB node 1 (e.g., 502 ₁) and the gNB-DU (e.g.,504). However, under the proposed solution, the aggregation of UEbearers into backhaul bearers can be performed not only based on the QoSclass of the aggregated bearers but also based on one of more factors,including routing information. One specific example of beareraggregation based on a combination of routing information and QoS classis provided as follows: 1) bearers for UE2 (e.g., 102 ₂) and UE3 (e.g.,102 ₃) with the same QoS class can be aggregated into the same backhaulbearer over link 1, link 2, and link 3; 2) bearers with the same QoSclass for UE1 and UE2 (e.g., 102 ₁) can be aggregated into a separatebackhaul bearer for link 2 and link 1; and 3) bearers with the same QoSclass for UE4 (e.g., 102 ₄) can be aggregated into separate backhaulbearers over link 4 and link 1. In order to perform bearer aggregationbased on routing information, the routing information for each UE bearercan be provided to IAB nodes that are performing the bearer aggregation.

In another embodiment, a topology/routing entity in the network canenforce certain aggregation policies at the individual IAB nodes (viaoperations administration management (OAM) or cyclic prefix (CP)interface etc.). For example, the topology and/or routing entity cansend enforcement policies to IAB nodes instructing which factors toconsider when performing aggregation of bearers. Additionally, suchenforcement policies can be modified over time based on network andtraffic conditions. Furthermore, this can work in reverse. For example,in order to try and maintain certain QoS and/or scheduling performance,topology changes can be triggered to limit the degree of beareraggregation in some cases (if certain links are identified asbottlenecks).

In yet another embodiment, assuming that the aggregated backhaul bearersare already set up in the way described in the first solution, then whenthere is a mobility event, the backhaul bearer aggregation can bereconfigured along various IAB links. For example, when UE3 (e.g., 102₃) performs a handover from IAB node 3 (e.g., 502 ₃) to IAB node 4(e.g., 502 ₄), UE3's (e.g., 102 ₃) bearers that have the same QoS classas the bearers of UE4 (e.g., 102 ₄), can now be aggregated into a commonbackhaul bearer over IAB link 4 and IAB link 1. Hence, the backhaulbearers that were already setup over IAB link 4 and link 1 for UE4 (102₄) can be reconfigured to add the bearers for UE3 (e.g., 102 ₃).Moreover, the aggregated backhaul bearers that were set up over link 3,link 2, and link 1 to aggregated bearers from UE2 (e.g., 102 ₂) and UE3(e.g., 102 ₃) can now be reconfigured to remove bearers for UE3 (e.g.,102 ₃).

In another embodiment, when link 3 between IAB node 3 (e.g., 502 ₃) andIAB node 2 (e.g., 502 ₂) experiences poor radio frequency (RF)performance, the traffic to/from UE2 (e.g., 102 ₂) and UE3 (e.g., 102 ₃)bearers can experience a route change to traverse from IAB Node 3 to IABNode 4 to IAB Node 1 (e.g., 502 ₁) to gNB-DU (e.g., 504). As a result ofthis route change, the bearers for UE2 (e.g., 102 ₂) and UE3 (e.g., 102₃) can be aggregated into common backhaul bearers across UE2 (e.g., 102₂), UE3 (e.g., 102 ₃) and UE4 (e.g., 102 ₄) over link 4 and link 1. Itshould be noted that in this example, a new aggregated backhaul bearercan be set up to aggregate bearers for UE2 (e.g., 102 ₂) and UE3 (e.g.,102 ₃) over a link 5. Additionally, the reconfiguration of aggregatedbackhaul bearers can also be performed to maintain certain performancemetrics, such as QoS requirement of UE bearers, or some other networkperformance metrics.

Referring now to FIG. 9 , illustrates an example flow diagram forfacilitating configuration and reconfiguration of aggregated backhaulbearers. At element 900, a method can comprise receiving first data froma first mobile device (e.g., UE 102 ₁) of a wireless network via a firstmobile device bearer channel. At element 902, the method can comprisereceiving second data from a second mobile device (e.g., UE 102 ₂), ofthe wireless network via a second mobile device bearer channel.Additionally, at element 904, the method can comprise in response to thereceiving the first data from the first mobile device (e.g., UE 102 ₁)and the receiving the second data from the second mobile device (e.g.,UE 102 ₂), aggregating, by the wireless network device, the first dataand the second data, resulting in aggregated data for a backhaul bearerof the wireless network, wherein the aggregating the first data and thesecond data is based on a first condition associated with a quality ofservice of the first mobile device (e.g., UE 102 ₁) bearer channel beingdetermined to have been satisfied and a second condition associated witha data route of the first data being determined to have been satisfied.

Referring now to FIG. 10 , illustrated is an example flow diagram forfacilitating configuration and reconfiguration of aggregated backhaulbearers. At element 1000, a system can facilitate, receiving first datafrom a first mobile device (e.g., UE 102 ₁) via a first bearer channelof a wireless network. At element 1002, the system can also comprisereceiving second data from a second mobile device (e.g., UE 102 ₂) via asecond bearer channel of the wireless network. Additionally, in responseto the receiving the first data from the first mobile device (e.g., UE102 ₁) and the receiving the second data from the second mobile device(e.g., UE 102 ₂), and in response to an aggregation condition associatedwith a routing pattern and a quality of service being determined to havebeen satisfied, aggregating the first data and the second data,resulting in aggregated data for use in connection with a backhaulbearer of the wireless network at element 1004.

Referring now to FIG. 11 , illustrated is an example flow diagram forfacilitating configuration and reconfiguration of aggregated backhaulbearers. At element 1100, a machine-readable medium can comprisereceiving first data from a first mobile device (e.g., UE 102 ₁) via afirst bearer channel. At element 1102, the machine-readable storagemedium can perform the operations comprising receiving second data froma second mobile device (e.g., UE 102 ₂) via a second bearer channel.Furthermore, in response to the receiving the first data from the firstmobile device (e.g., UE 102 ₁) and the receiving the second data fromthe second mobile device (e.g., UE 102 ₂) and in response to a routingcondition and a quality of service of the second bearer channel beingdetermined to have been satisfied, the machine-readable storage mediumcan perform the operations comprising aggregating the first data and thesecond data, resulting in aggregated data to be utilized by a backhaulbearer at element 1104.

Referring now to FIG. 12 , illustrated is a schematic block diagram ofan exemplary end-user device such as a mobile device 1200 capable ofconnecting to a network in accordance with some embodiments describedherein. Although a mobile handset 1200 is illustrated herein, it will beunderstood that other devices can be a mobile device, and that themobile handset 1200 is merely illustrated to provide context for theembodiments of the various embodiments described herein. The followingdiscussion is intended to provide a brief, general description of anexample of a suitable environment 1200 in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset 1200 includes a processor 1202 for controlling andprocessing all onboard operations and functions. A memory 1204interfaces to the processor 1202 for storage of data and one or moreapplications 1206 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 1206 can be stored in thememory 1204 and/or in a firmware 1208, and executed by the processor1202 from either or both the memory 1204 or/and the firmware 1208. Thefirmware 1208 can also store startup code for execution in initializingthe handset 1200. A communications component 1210 interfaces to theprocessor 1202 to facilitate wired/wireless communication with externalsystems, e.g., cellular networks, VoIP networks, and so on. Here, thecommunications component 1210 can also include a suitable cellulartransceiver 1211 (e.g., a GSM transceiver) and/or an unlicensedtransceiver 1213 (e.g., Wi-Fi, WiMax) for corresponding signalcommunications. The handset 1200 can be a device such as a cellulartelephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 1210 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The handset 1200 includes a display 1212 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1212 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1212 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1214 is provided in communication with the processor 1202 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 1200, for example. Audio capabilities areprovided with an audio I/O component 1216, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 1216 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 1200 can include a slot interface 1218 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 1220, and interfacingthe SIM card 1220 with the processor 1202. However, it is to beappreciated that the SIM card 1220 can be manufactured into the handset1200, and updated by downloading data and software.

The handset 1200 can process IP data traffic through the communicationcomponent 1210 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 800 and IP-based multimediacontent can be received in either an encoded or decoded format.

A video processing component 1222 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1222can aid in facilitating the generation, editing and sharing of videoquotes. The handset 1200 also includes a power source 1224 in the formof batteries and/or an AC power subsystem, which power source 1224 caninterface to an external power system or charging equipment (not shown)by a power I/O component 1226.

The handset 1200 can also include a video component 1230 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 1230 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1232 facilitates geographically locating the handset 1200. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 1234facilitates the user initiating the quality feedback signal. The userinput component 1234 can also facilitate the generation, editing andsharing of video quotes. The user input component 1234 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1206, a hysteresis component 1236facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1238 can be provided that facilitatestriggering of the hysteresis component 1238 when the Wi-Fi transceiver1213 detects the beacon of the access point. A SIP client 1240 enablesthe handset 1200 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 1206 can also include aclient 1242 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 1200, as indicated above related to the communicationscomponent 810, includes an indoor network radio transceiver 1213 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 1200. The handset 1200 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 13 , there is illustrated a block diagram of acomputer 1300 operable to execute a system architecture that facilitatesestablishing a transaction between an entity and a third party. Thecomputer 1300 can provide networking and communication capabilitiesbetween a wired or wireless communication network and a server (e.g.,Microsoft server) and/or communication device. In order to provideadditional context for various aspects thereof, FIG. 13 and thefollowing discussion are intended to provide a brief, generaldescription of a suitable computing environment in which the variousaspects of the innovation can be implemented to facilitate theestablishment of a transaction between an entity and a third party.While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the innovation also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the innovation can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 13 , implementing various aspects describedherein with regards to the end-user device can include a computer 1300,the computer 1300 including a processing unit 1304, a system memory 1306and a system bus 1308. The system bus 1308 couples system componentsincluding, but not limited to, the system memory 1306 to the processingunit 1304. The processing unit 1304 can be any of various commerciallyavailable processors. Dual microprocessors and other multi processorarchitectures can also be employed as the processing unit 1304.

The system bus 1308 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1306includes read-only memory (ROM) 1327 and random access memory (RAM)1312. A basic input/output system (BIOS) is stored in a non-volatilememory 1327 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1300, such as during start-up. The RAM 1312 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1300 further includes an internal hard disk drive (HDD)1314 (e.g., EIDE, SATA), which internal hard disk drive 1314 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1316, (e.g., to read from or write to aremovable diskette 1318) and an optical disk drive 1320, (e.g., readinga CD-ROM disk 1322 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1314, magnetic diskdrive 1316 and optical disk drive 1320 can be connected to the systembus 1308 by a hard disk drive interface 1324, a magnetic disk driveinterface 1326 and an optical drive interface 1328, respectively. Theinterface 1324 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject innovation.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1300 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1300, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the exemplary operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed innovation.

A number of program modules can be stored in the drives and RAM 1312,including an operating system 1330, one or more application programs1332, other program modules 1334 and program data 1336. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1312. It is to be appreciated that the innovation canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1300 throughone or more wired/wireless input devices, e.g., a keyboard 1338 and apointing device, such as a mouse 1340. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1304 through an input deviceinterface 1342 that is coupled to the system bus 1308, but can beconnected by other interfaces, such as a parallel port, an IEEE 2394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1344 or other type of display device is also connected to thesystem bus 1308 through an interface, such as a video adapter 1346. Inaddition to the monitor 1344, a computer 1300 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1300 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1348. The remotecomputer(s) 1348 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 1350 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1352 and/or larger networks,e.g., a wide area network (WAN) 1354. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1300 isconnected to the local network 1352 through a wired and/or wirelesscommunication network interface or adapter 1356. The adapter 1356 mayfacilitate wired or wireless communication to the LAN 1352, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1356.

When used in a WAN networking environment, the computer 1300 can includea modem 1358, or is connected to a communications server on the WAN1354, or has other means for establishing communications over the WAN1354, such as by way of the Internet. The modem 1358, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1308 through the input device interface 1342. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1350. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

Current solutions do not consider other factors, such as routinginformation to decide which UE bearers can be aggregated into commonbackhaul bearers. This can cause problems when UE bearers for UE1 andUE2 are aggregated into a common backhaul bearer between the donor IABnode and IAB node 1. However, from IAB node 1 onwards, the two UEbearers can take different routes to reach UE1 and UE2 (assuming UE1 andUE2 are being served by different IAB nodes). In this case, if the routeto UE1 is congested or has a poor link, any hop-by-hop flow controlmechanism that operates on a per-RLC channel level between the donor IABnode and IAB node 1 can cause conflicting results for UE bearers 1 and2. For example if the backhaul bearer is throttled based on detectedcongestion for UE bearer 1, it can unnecessarily punish UE bearer 2.

Current solutions for bearer aggregation do not address the need forbearer reconfiguration upon route changes or RRM events. For example, ifUE bearers for UE1 and UE2 are aggregated into a common backhaul bearerbetween the donor IAB node and IAB node 1 because they follow a commonroute to the same access IAB node, and UE1 moves away to a differentaccess IAB node, depending upon conditions, it can be better toreconfigure the UE bearers aggregated in to the backhaul channel (RLCchannel) between donor IAB node and IAB node 1 to prevent the problemdescribed.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the subject matter has been described herein inconnection with various embodiments and corresponding FIGs, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A method, comprising: receiving, by networkequipment comprising a processor, first data from a first user equipmentvia a first user equipment bearer channel enabled via a network;receiving, by the network equipment, second data from a second userequipment via a second user equipment bearer channel enabled via thenetwork; in response to a performance metric of the first user equipmentbearer channel being determined to have been satisfied: aggregating, bythe network equipment, the first data and the second data, resulting inaggregated data for a backhaul bearer enabled via the network, andinitiating, by the network equipment, a network equipment topologymodification to restrict aggregation of third data from a third userequipment with the aggregated data for the backhaul bearer to maintainthe performance metric of the first user equipment bearer channel. 2.The method of claim 1, further comprising: sending, by the networkequipment, the aggregated data to be applied to the backhaul bearer. 3.The method of claim 1, wherein the aggregating is based on a conditionis associated with a routing of the first data to the backhaul bearerbeing determined to have been satisfied.
 4. The method of claim 1,further comprising: receiving, by the network equipment, routing datarepresentative of a route via which the first data is to becommunicated.
 5. The method of claim 1, further comprising: receiving,by the network equipment, routing data representative of a first routevia which the second data is to be communicated as an alternative to asecond route of the routing data.
 6. The method of claim 1, furthercomprising: modifying, by the network equipment, the aggregated databased on a second quality of service, different than a first quality ofservice associated with the backhaul bearer.
 7. The method of claim 1,further comprising: receiving, by the network equipment, policy datarepresentative of a policy to which the network equipment is to adhere,during the aggregating of the first data and the second data.
 8. Themethod of claim 1, wherein aggregating the first data and the seconddata is further based on a second condition associated with a data routeof the first data being determined to have been satisfied.
 9. The methodof claim 1, further comprising: in response to a handover of the firstdata from first node equipment to second node equipment, reconfiguring,by the network equipment, the aggregated data to be further applied tothe backhaul bearer.
 10. The method of claim 1, further comprising:limiting, by the network equipment, an amount of the first data and thesecond data to be aggregated according to the aggregating.
 11. A system,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: receiving first data from a firstuser equipment via a first network bearer channel; receiving second datafrom a second user equipment via a second network bearer channel; inresponse to a performance criterion associated with a routing patternbeing determined to have been satisfied: aggregating the first data andthe second data, resulting in aggregated data for use in connection witha network backhaul bearer, and triggering a network topologymodification to restrict aggregation of third data from a third userequipment with the aggregated data for use in the connection with thenetwork backhaul bearer to maintain a quality of service of the firstuser equipment bearer channel.
 12. The system of claim 11, wherein therouting pattern is associated with a route of the first data.
 13. Thesystem of claim 11, wherein the operations further comprise: sendingroute data representative of a route of the first data to integratedaccess backhaul node equipment to facilitate aggregating of the firstdata and the second data.
 14. The system of claim 11, wherein theoperations further comprise: sending quality of service datarepresentative of the quality of service to integrated access backhaulnode equipment to facilitate aggregating of the first data and thesecond data.
 15. A non-transitory machine-readable medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: receiving first data from a firstmobile device via a first bearer channel; receiving second data from asecond mobile device via a second bearer channel; in response to achannel performance metric of the second bearer channel being determinedto have been satisfied: aggregating the first data and the second data,resulting in aggregated data to be utilized by a backhaul bearer,modifying a topology to preclude aggregation of third data from a thirdmobile device with the aggregated data to be utilized by the backhaulbearer to maintain the channel performance metric of the second bearerchannel.
 16. The non-transitory machine-readable medium of claim 15,wherein a routing condition is associated with sending a first route ofthe first data and a second route of the second data to an integratedaccess backhaul node to facilitate the aggregating the first data andthe second data.
 17. The non-transitory machine-readable medium of claim15, wherein the channel performance metric is a first channelperformance metric, and wherein the aggregating is based on a secondchannel performance metric associated with the first bearer channel. 18.The non-transitory machine-readable medium of claim 17, wherein theoperations further comprise: in response to a condition associated withthe second channel performance metric being determined to have beensatisfied, reconfiguring the backhaul bearer by modifying the aggregateddata.
 19. The non-transitory machine-readable medium of claim 18,wherein reconfiguring the aggregated data comprises removing the firstbearer channel from the aggregated data.
 20. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise: sending the aggregated data to be utilized by the backhaulbearer.